Pipeline

您所在的位置：网站首页 › k8s in action pdf › Pipeline

Pipeline

#Pipeline| 来源: 网络整理| 查看: 265

K8S API for PipelineK8S API for Pipeline

Compared with the Application Workflow, the standalone pipeline has the following characteristics:

It can manage multiple KubeVela Applications across multiple environments.It is not bound to Applications and can be used independently. For example, it can expand or shrink a set of resources, perform process-oriented canary publishing for an Application, and perform a set of operation and maintenance operations in batches.It is one-time and does not manage resources. Even if the pipeline is deleted, the created resources will not be deleted.It uses the same execution engine as the Application Workflow, which completely inherits the features of KubeVela’s lightweight workflow. Compared with the traditional container-based CI pipeline, KubeVela’s pipeline does not depend on containers, No additional computing resources are required.

tip

In order to better reuse the existing capabilities and ensure technical consistency, we split the workflow engine part of the original application workflow. Both in-application workflow and pipeline use this workflow engine as the underlying technology implementation. The application workflow is represented by the Workflow field in the application, and the pipeline is represented by the WorkflowRun resource.

This means that most of the workflow steps are common between the two, such as: suspend, notification, send HTTP request, read configuration, etc.

However, in WorkflowRun, there is only the configuration of steps, and no configuration of components, traits, and policies. Therefore, steps related to components/traits/policy can only be used in in-app workflows, such as: deploying/updating components, traits, etc.

Please make sure that you have enabled workflow addon:

vela addon enable vela-workflow

WorkflowRun is the K8S API for pipeline. You can choose to execute an external Workflow template in the WorkflowRun or execute the steps in the WorkflowRun spec (if you declare both, the step in the WorkflowRun spec will override the content in the template). A WorkflowRun consists of the following:

apiVersion: core.oam.dev/v1alpha1kind: WorkflowRunmetadata: name: namespace: spec: mode: steps: subSteps: context: workflowRef: workflowSpec: steps: - name: type: dependsOn: meta: alias: properties: if: timeout: outputs: - name: valueFrom: inputs: - name: parameterKey:

【本文地址】

Pipeline

Pipeline

今日新闻

推荐新闻